Skip to content

docs: add governance section #7675

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

docs: add governance section #7675

wants to merge 2 commits into from

Conversation

Jatinyadav29
Copy link

Summary

This pull request adds a "Governance" section to the documentation.
The content is adapted from the [webpack/governance](https://github.com/webpack/governance) repository’s README file and converted into MDX format to align with the webpack.js.org documentation style and structure.

Related Issue

Fixes [#7333](#7333)

Changes Introduced

  • Added new file: src/content/contribute/governance.mdx

  • Converted markdown to MDX format with frontmatter and internal link structure

  • Added YAML frontmatter:

    ---
title: Webpack Project Governance
sort: 15
contributors:
  - Jatinyadav29
---

  • Ensured compatibility with the docs build and navigation hierarchy

Preview

The new page introduces details about:

  • Roles and responsibilities (Contributors, Committers, Reviewers)
  • The Technical Steering Committee (TSC)
  • The Consensus Seeking Process

It provides transparency into webpack’s governance model, adapted from Node.js and ESLint governance frameworks.

Checklist

  • Converted README to MDX format
  • Added appropriate frontmatter and metadata
  • Verified formatting and link consistency
  • Local build runs without errors
  • Linked to the correct issue and mentioned it in the PR body

💡 Note: Since I’m still new to the webpack documentation setup, I took extra care to follow the contributing and writer’s guide. Please feel free to suggest any improvements or formatting changes.
Screenshot 2025-10-07 at 8 01 47 PM

@vercel Vercel
Copy link

vercel bot commented Oct 7, 2025

@Jatin29yadav is attempting to deploy a commit to the OpenJS Foundation Team on Vercel.

A member of the Team first needs to authorize it.

@linux-foundation-easycla Linux Foundation: EasyCLA
Copy link

linux-foundation-easycla bot commented Oct 7, 2025 •
edited
Loading

CLA Signed

The committers listed above are authorized under a signed CLA.

@Jatinyadav29 Jatinyadav29 force-pushed the fix-governance-section branch from 6357918 to a6d8c6b Compare October 7, 2025 15:32
@vercel Vercel
Copy link

vercel bot commented Oct 7, 2025 •
edited
Loading

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Preview Comments Updated (UTC)
webpack-js-org Ready Ready Preview Comment Oct 7, 2025 10:00pm

evenstensberg
evenstensberg requested changes Oct 7, 2025
View reviewed changes
Copy link
Member

@evenstensberg evenstensberg left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice work here. Could you revert the lockfile and version bumps?

I've accepted preview of this PR so we can see the visual of the pr.

evenstensberg
evenstensberg requested changes Oct 7, 2025
View reviewed changes
Copy link
Member

@evenstensberg evenstensberg left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

all these also needs to be added. Add them as subsections.

Image

@Jatinyadav29
Copy link
Author

Jatinyadav29 commented Oct 8, 2025 •
edited
Loading

Hey @eventensberg
All requested changes have been addressed:

Governance section and subsections added under /src/content/contribute/governance/

Markdown lint issues (MD025, MD052) fixed

Verified locally (yarn start) — all pages render correctly

yarn.lock reverted and untouched

CLA and lint checks have passed successfully
The Vercel check is authorization-related and expected for contributors.

Ready for re-review and merge

@alexander-akait
Copy link
Member

@evenstensberg Can we write a script that fetch these files from webpack, because if we will need to change it it will require to make changes in both places, it is not good

@Jatinyadav29
Copy link
Author

Jatinyadav29 commented Oct 8, 2025 •
edited
Loading

Thanks for the feedback @alexander-akait and @evenstensberg
The idea of automating governance content sync from the webpack/governance repo makes complete sense for long-term maintainability.

For this PR, I’ve focused on adding the initial Governance section and ensuring it’s integrated properly in /src/content/contribute/governance/.

Everything now builds and renders correctly — ready for re-review whenever you’re available

@evenstensberg
Copy link
Member

Let's try to implement this correct on the first pass.

@Jatinyadav29 could you try to tackle this issue? It will make it better for you because then you can learn how the docs site really works.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@evenstensberg evenstensberg Awaiting requested review from evenstensberg

Requested changes must be addressed to merge this pull request.

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@Jatinyadav29 @alexander-akait @evenstensberg